home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
rastat10.zip
/
RASTAT.DOC
< prev
next >
Wrap
Text File
|
1992-05-25
|
36KB
|
815 lines
RAStat Documentation Page 01 of 14
════════════════════════════════════════════════════════════════════════
RAStat v1.00 ── RemoteAccess Statistical Generator
Program and documentation copyright (c) 1992 Gary Ryno.
All rights reserved.
Program Description:
────────────────────
RAStat is a full-featured statistical tool and display generator for
RemoteAccess Bulletin Board Systems.
The program generates general information, system statistics, top user
and recent caller information in a RemoteAccess environment. In
addition to its RA-specific features, RAStat has optional, enhanced
capabilities for systems that also operate FrontDoor. RAStat produces
crisp ASCII and ANSI output files, which are properly formatted for
display from RA, using the type-5 menu option.
Some of RAStat's principle features include:
■ Generation of overall system statistics: total upload/download/
message activity by current users, message base info, system calls,
etc.
■ Generation of "top ten" user statistics: top callers, message
writers, uploaders and downloaders (both number of files and
kbytes).
■ Generation of "today's calls" information: user calls, and
(optionally in a FrontDoor environment) inbound/outbound mailer
calls.
■ A high degree of flexibility and SysOp control: configuration,
operating modes, feature toggles, colors for ANSI output files, etc.
■ Rapid execution speed.
Warranty and Disclaimer:
────────────────────────
In three words, none and everything.
RAStat is provided as-is, without warranty of any kind. The program's
user assumes full responsibility for the use of this program, its
output, and its accompanying documentation, and for any harm or
consequences arising from such use.
RAStat Documentation Page 02 of 14
════════════════════════════════════════════════════════════════════════
The program's author makes no warranty of any kind, either express or
implied, including, but not limited to, implied warranties of
merchantability or fitness for a particular purpose, with respect to
this software and accompanying documentation.
In no event will the program's author be liable for damages of any kind
arising from the use of this program, its output, or its accompanying
documentation. Use of this program constitutes acceptance of the above
provisions.
License:
────────
RAStat and its accompanying documentation are copyright (c) 1992 by
Gary Ryno. All rights are reserved.
License is granted to use RAStat for any non-commercial application,
without compensation to the program's author. RAStat is neither public
domain software or shareware; it is simply provided free of charge for
non-commercial uses. You may not use RAStat for any commercial
application, ie: any purpose that earns or is intended to earn a profit,
or to further for-profit business activities.
RAStat may be freely copied and distributed on magnetic or optical
media, or transmitted via modem, so long as no charge is levied for such
distribution. Any copies so distributed shall include the executables,
support file(s) and accompanying documentation in their complete,
original, unmodified form.
Neither the program or the accompanying documentation may be modified in
any way without the express written permission of the program's author.
The RAStat files may, of course, be compressed or archived using any
compression format.
Any use or distribution of this program beyond the scope of the license
described above, without the express written permission of the program's
author, constitutes a violation of copyright.
Why RAStat? Wither the hobbyist? (a brief, blunt editorial):
──────────────────────────────────────────────────────────────
I'm a veteran SysOp. Why did I write RAStat?
There are many other stat/info/call utilities available for
RemoteAccess. Frankly, few are very impressive.
Worse than the programs are the attitudes of some programmers. Almost
every one of these gadgets was written by some poor, misguided fool who
expected to be sent money, mailed postcards, or otherwise paid homage
for having bestowed this junk on an innocent, unsuspecting world.
Toward that end, almost every one of their programs was crippled,
keycoded or deliberately annoying.
RAStat Documentation Page 03 of 14
════════════════════════════════════════════════════════════════════════
I get very perturbed whenever I encounter a minor BBS utility that's
littered with annoying "register me" garbage, has a drop-dead date, or
requires a keycode to run. I imagine most other SysOps feel the same
way. In BBS circles, this trend has reached the ludicrous stage.
Running a BBS ── and programming BBS utilities ── is a hobby for most of
us, a way we've deliberately chosen to spend our leisure time. It's
supposed to be fun. Somewhere along the line, quite a few people seem
have forgotten that simple premise. The best and the brightest started
coding BBS software a good number of years ago, observing such credos as
"absolutely free" and "militantly public domain". Matter of fact, they
still do. It's time everyone else got back to such a mindset.
End of sermon.
Use RAStat as you see fit. It's free. I hope you find it handy.
Hardware and Software Requirements:
───────────────────────────────────
RAStat requires RemoteAccess, unconditionally. If you're not running a
RemoteAccess BBS, then RAStat is useless to you.
RAStat will run on any IBM PC/XT/AT or compatible, under DOS v3.00 or
later. The program executables require about 85 kb of diskspace.
Modest additional diskspace will also be needed for its control and
output files.
The program's memory needs vary somewhat, depending on the operating
mode and the size of your USERS.BBS and other system files. Unless your
system files are unusually large, 220kb of RAM will typically be
sufficient. In any event, RAStat should run in any memory window that
is satisfactory for either RA or FD.
RAStat has been tested successfully under DESQview, however has no
specific DV-aware features. It has not been tested in any other
multitasking environment.
The RAStat executables have been successfully tested after being
compressed with both PKLite and LZExe. RAStat has not been tested under
Stacker, or using any other method of runtime compression/decompression.
RAStat is hardcoded for the file structures used by RemoteAccess v1.11
and (optionally) FrontDoor v2.02/nc. It has not been tested with
earlier, obsolete versions of either program. It will continue to work
with later versions of both programs, so long as the structures of the
USERS.BBS, LASTCALL.BBS, INBOUND.HIS and OUTBOUND.HIS files remain
substantially unchanged.
RAStat Documentation Page 04 of 14
════════════════════════════════════════════════════════════════════════
Program Installation:
─────────────────────
As distributed, the complete RAStat package consists of seven files:
■ RASTAT.EXE [program executables]
■ RASTAT.CTL [sample control file]
■ RASTAT.DOC [documentation]
■ STATS.A?? [two sample stats mode output files, ASCII and ANSI]
■ CALLS.A?? [two sample calls mode output files, ASCII and ANSI]
Only RASTAT.EXE and RASTAT.CTL are necessary for the program's
operation. RAStat may be installed and run from anywhere on the system;
simply copy RASTAT.EXE and RASTAT.CTL to the desired directory.
There is one important factor to consider during installation: the
RASTAT.CTL file will need to be in the current directory when the
program is run. Having this in mind, the flow of your system's batch
file(s) will best dictate where RAStat should be installed. On the
typical BBS, the RA system directory is the most convenient place.
Program Configuration:
──────────────────────
RAStat requires its own control file, RASTAT.CTL. Everything the
program needs to know is contained in this single file; it doesn't need
to have the RA or FD environment variables set, nor does it care about
the *.RA or *.FD files. This approach was selected to make RAStat
adaptable to virtually any system.
The control file is flat ASCII text. It may be edited with DOS EDLIN, a
text editor, or a word processor (in the latter case, be certain to save
the file in non-document mode, ie: as raw ASCII text).
The control file MUST be named RASTAT.CTL, and again, it MUST be in the
current directory when RAStat is executed. If RAStat is unable to find
and/or read the control file, the program will abort.
The fastest way to get RAStat up and running is to edit the sample
RASTAT.CTL file to fit your system and needs. The sample file is
heavily commented, and should be largely self-explanatory. It is
explained in greater detail below.
RASTAT.CTL may contain as many comment lines as you wish. Comment lines
begin with a semicolon (;) as the first character, and are ignored by
the program. No comment lines are required; without them, a small
amount of diskspace will be saved, and the program will initialize
slightly faster.
Non-comment lines in RASTAT.CTL begin with a keyword. All valid
keywords and their correct usage are detailed below. Keywords are case
insensitive, and may appear in RASTAT.CTL in any order. Keywords must
be spelled exactly as shown below, and they may not be proceeded by
spaces.
RAStat Documentation Page 05 of 14
════════════════════════════════════════════════════════════════════════
Several keywords require a parameter. There must be EXACTLY one blank
space (not three spaces, or two, or a tab, but ONE space) between the
keyword and the parameter.
Several keywords require a DOS path as a parameter. The paths specified
in the control file MUST exist; RAStat will not create them, and the
program will abort if they don't exist. A trailing backslash (\) is
optional on all path parameters.
Several keywords toggle features on/off. In the sample control file,
all are enabled by default. To disable these features, comment-out the
keyword with a semicolon.
All keyword lines in the control file MUST be terminated by a CRLF
immediately after the last significant text character; trailing spaces
or trailing comments are NOT permitted (for the non-technical reader:
press [Enter] after the last character on the line).
Invalid lines and invalid keywords will either cause RAStat to abort, or
will be ignored by the program, depending on the circumstances.
A detailed description of each keyword and its correct usage follows
(stats mode and calls mode are explained under "Program Operation").
■ BBSName [usage: BBSName Name]
The name of your BBS. The name is used by RAStat to personalize its
output files to your system. The BBSName parameter may be up to 30
characters long, and may include any printable character, including
spaces. Excess characters are truncated. BBSName is mandatory for
all modes.
■ RAPath [usage: RAPath c:\ra\]
The complete path to your RemoteAccess USERS.BBS and LASTCALL.BBS
files, as defined in CONFIG.RA. RAPath is mandatory for all modes.
■ TextPath [usage: TextPath c:\ra\text\]
The complete path to the directory where RAStat is to write its
output files. Normally, this should be the RA textfiles directory,
as defined in CONFIG.RA. However, if you have special needs, you
can specify any directory on the system. TextPath is mandatory for
all modes.
■ FDPath [usage: FDPath c:\fd\]
The complete path to your FrontDoor INBOUND.HIS and OUTBOUND.HIS
files, as defined in SETUP.FD. FDPath is mandatory for calls
mode if FDCalls is enabled, and is ignored otherwise.
RAStat Documentation Page 06 of 14
════════════════════════════════════════════════════════════════════════
■ StatsFile [usage: StatsFile filename]
The base filename for the stats mode output files. These files will
be written to the TextPath directory, using the name specified, in
both ASCII and ANSI format. Do NOT include a path or extension with
the filename; RAStat will insert them. StatsFile is mandatory for
stats mode, and is ignored otherwise.
■ CallsFile [usage: CallsFile filename]
The base filename for the calls mode output files. These files will
be written to the TextPath directory, using the name specified, in
both ASCII and ANSI formats. Do NOT include a path or extension
with the filename; RAStat will insert them. StatsFile is mandatory
for stats mode, and is ignored otherwise.
Note: StatsFile and CallsFile MUST each specify a unique filename.
DON'T try using the same filename for both, it will NOT work!
■ FDCalls [usage: FDCalls]
This parameter tells RAStat whether or not to generate FD mailer
call information when running in calls mode. If FDCalls is enabled,
the day's mailer calls will be detailed in the calls mode output
files, in addition to the day's user calls. Comment-out to disable.
FDCalls is optional for calls mode, and is ignored otherwise.
■ SysopExclude [usage: SysopExclude]
This parameter tells RAStat whether or not to exclude the SysOp
(defined as the first record in USERS.BBS) from its output files.
If SysopExclude is enabled, then the first user in USERS.BBS will
NEVER appear in any of RAStat's output files. Comment-out to
disable. SysopExclude is optional, and affects all modes.
■ HiddenExclude [usage: HiddenExclude]
This parameter tells RAStat whether or not to exclude users who have
the hidden attribute set in USERS.BBS from its output files. If
HiddenExclude is enabled, then users with the hidden attribute set
will NEVER appear in RAStat's output files. Comment-out to disable.
HiddenExclude is optional, and affects all modes.
■ Quiet [usage: Quiet]
RAStat only beeps the speaker (once) if an error occurs. If the
Quiet parameter is enabled, ALL speaker sounds are silenced while
the program is running. Comment-out to disable. Quiet is optional,
anf affects all modes.
Note: There is one exception to Quiet mode. If RAStat aborts
because it cannot find and/or read the RASTAT.CTL file, it
WILL beep the speaker once, unconditionally.
RAStat Documentation Page 07 of 14
════════════════════════════════════════════════════════════════════════
■ Title [usage: Title ##]
■ Header [usage: Header ##]
■ Data [usage: Data ##]
■ Prompt [usage: Prompt ##]
■ Background [usage: Background ##]
These parameters specify the colors to be used in each field in the
ANSI output files. Only one background color is permitted; the
other keywords all specify foreground colors for each of the various
fields. A list of the available colors and their corresponding
numbers follows below. The color parameters are mandatory for all
modes.
To start, it is recommended that you view the sample ANSI files
included with RAStat. They were generated using the default colors
specified in the sample control file. Once you have a feel for the
various fields, adjust the colors to suit your preferences.
Note: RAStat only checks the color parameters for numeric validity
(ie: if you specify a number outside of the valid ranges, such
as a foreground-only color for the background, the program
will abort).
RAStat does NOT check the colors for visual/aesthetic
characteristics. If you specify hideous color combinations,
RAStat will merrily generate them for you. Ditto, if you
specify black on black, that's exactly what you'll get: an
all-black, apparently blank field.
Valid color parameters:
Background Foreground
──────────── ─────────────────────────────────
00 = Black 00 = Black 08 = Dark grey
01 = Blue 01 = Blue 09 = Bright blue
02 = Green 02 = Green 10 = Bright green
03 = Cyan 03 = Cyan 11 = Bright cyan
04 = Red 04 = Red 12 = Bright red
05 = Magenta 05 = Magenta 13 = Bright magenta
06 = Brown 06 = Brown 14 = Bright yellow
07 = Gray 07 = Gray 15 = Bright white
Program Operation:
──────────────────
RAStat has two different operating modes: stats and calls. They are
totally independent from each other. At your option, you may use either
or both.
The operating mode(s) are specified by DOS command line parameter:
■ rastat -stats [generate statistical and top user files only]
■ rastat -calls [generate today's calls files only]
■ rastat -stats -calls [generate both]
RAStat Documentation Page 08 of 14
════════════════════════════════════════════════════════════════════════
RAStat has no other command line parameters. The parameters are case
insensitive, and may appear in any order. They may be prefaced by a
dash (-), a forward slash (/), or a blank space; the program can handle
all three forms. RAStat will abort to a help screen if at least one
valid parameter isn't specified on the command line. Invalid parameters
are otherwise ignored.
In stats mode, RAStat generates ASCII and ANSI files depicting general
system information, an overall statistical summary of user activity, and
the system's top ten users in each of six different categories (logons,
messages posted, files uploaded, kbytes uploaded, files downloaded, and
kbytes downloaded).
The "general info" portion of the stats output files utilize several
imbedded RA control codes, to display real-time information when the
file is viewed from RA. These include the current date and time, time
to the next event, total number of logons, total number of users, and a
message base summary.
In calls mode, RAStat generates ASCII and ANSI files depicting the day's
BBS calls, including each caller's name, location, number of calls, BPS
rate and on/off time, and a running total of the day's total logons.
In a FrontDoor environment, the calls output files will also include the
day's inbound/outbound mailer calls, if FDCalls is enabled. The FDCalls
output includes the remote link's node number and system name, bytes
received and sent, cost, session time, and a summary of the day's total
mail activity.
To get a better feel for the exact information that RAStat generates,
and to see how the data is formatted, please refer to the sample output
files. They illustrate the program's capabilities far more clearly than
would any long-winded description here.
RAStat is quite fast. No matter how often you choose to run the
program, it won't bog-down your system, or significantly increase its
recycle time. For example, it typically takes RAStat less than 10
seconds to do a full stats run on a 350-record USERS.BBS, using a modest
10 mhz AT-class machine. Calls mode is even faster; typically less than
5 seconds, even with FDCalls enabled and 500-record *.HIS files.
Obviously, actual execution time will depend on the speed of your
computer, and the size of your system files.
You can run stats mode as often or as seldom as you wish. Once per day
during your maintenance event is quite sufficient. Alternatively, if
you prefer the most up-to-the-minute data online at all times, stats
mode can be run periodically throughout the day, or after every user
logoff.
Calls mode has somewhat stricter requirements: in order to maintain
reasonably current files of the day's calls, calls mode needs to be run
at the proper times. At minimum, calls mode should be run after every
user logoff. If you have FDCalls enabled, you may prefer to do a calls
run just before loading FrontDoor each cycle, for the most
up-to-the-minute data.
RAStat Documentation Page 09 of 14
════════════════════════════════════════════════════════════════════════
As a starting point, you might try the setup I use on my own BBS:
RAStat -stats once per day during maintenance, and RAStat -calls before
each FrontDoor cycle. All output files can also be generated at once
during the same run: simply specify both -stats and -calls on the
command line.
Again, it must be stressed that stats mode and calls mode are completely
autonomous. Each mode performs a different function, and is totally
independent of the other. If you wish, you may use only stats mode.
Or only calls. Or both. However you choose to configure and operate
RAStat, the program will do precisely what you want it to.
Obviously, RAStat was designed for unattended operation, under batch
file control. It's entirely up to you to add the necessary lines to
your system's batch file(s) to invoke RAStat at the appropriate times.
Running RAStat manually when shelled from RA [Alt-J] is NOT recommended.
When running in either mode, RAStat needs access to your RemoteAccess
USERS.BBS and LASTCALL.BBS files. In calls mode with FDCalls enabled,
it also needs access to the FrontDoor INBOUND.HIS and OUTBOUND.HIS
files. If RAStat is unable to locate and/or read any of the files it
needs to operate in the current mode(s), it will abort. In these cases,
any pre-existing output files will remain unchanged.
When RAStat writes its output files to disk, the new files overwrite any
old files of the same name. Calls mode output files are automatically
reset each day, the first run after midnight.
If FDCalls is enabled, it makes no difference how long you retain
FrontDoor's *.HIS files. RAStat searches the *.HIS files for the first
record matching the current date, and then reads from that point to the
end of the file; even if your *.HIS files overlap multiple months, they
won't break RAStat.
Multiline Considerations:
─────────────────────────
When RAStat accesses the USERS.BBS, LASTCALL.BBS, INBOUND.HIS and
OUTBOUND.HIS files, it opens them as read-only, write-locked. They are
opened in this manner to absolutely protect them from any possible
corruption. If you run a multiline BBS, this may cause potential
sharing problems, should RA or FD try to open one of those files for
read/write access while RAStat has it open.
If the nature of your system is such that you need to prevent RAStat
from accessing the above files at certain times, it is ENTIRELY your
responsibility to prevent it from doing so by semaphoring as necessary
from your batch file(s). RAStat does NOT write semaphore files of its
own, and it does NOT look for semaphore files written by other programs.
In simplest terms, when you run RAStat, it runs. Unconditionally,
period.
RAStat Documentation Page 10 of 14
════════════════════════════════════════════════════════════════════════
Displaying RAStat's Output Files:
─────────────────────────────────
RAStat's ASCII and ANSI output files are always written to the TextFile
directory, named according to the specifications in RASTAT.CTL.
The output files are formatted for display from RemoteAccess, using RA
control codes. Each file is broken-down into multiple screens, each
separated by the usual "Press [Enter] to continue: ^A^L".
It's entirely up to you to setup the necessary RA menu commands to
display RAStat's output files on your BBS. You can display them however
you wish. They are best suited for online display using RA's type-5
textfile option. Alternatively, they may also be displayed from a
type-6 selection menu, as logon bulletins, or in any of several other
ways, limited only by RA's internal capabilities and your own
imagination.
It is suggested that you avoid using the RA display options that append
the "Press [Enter] to continue: ^A" sequence at the end of file.
RAStat's files already have them, and if you have RA append another,
your users will end-up needing to press [Enter] twice to return to the
menu.
As a starting point, you might try the setup I use on my own BBS: I keep
the RAStat output files in the RA textfiles directory, named STATS.A??
and CALLS.A??, and use a pair of type-5 options to display them.
Sample output files are included for your review. All of the RA control
codes have been removed from the samples. View the sample files using
the DOS TYPE [FILE.EXT] | MORE command... they are formatted to appear
roughly the same as the real files will appear when displayed from RA.
Although RemoteAccess supports AVATAR, RAStat does not have the
capability to generate files in the AVT/0+ format. This was a
deliberate programming decision. Rapid operation and reasonable
executable size were two key goals for RAStat. AVATAR hasn't yet
attained widespread use, and adding AVATAR support would have increased
RAStat's size and reduced its speed, for very little gain.
If AVATAR format files are critical to your system, you can easily
create them from RAStat's ANSI output files, using the AVTCONV
conversion utility; call AVTCONV from your batch file immediately after
RAStat is run. AVTCONV is currently being included in the RemoteAccess
distribution archives, and should also be available on any RA Support
System.
Program Limitations:
────────────────────
In general, RAStat's limitations parallel those imposed by the RA and FD
file structures. For example, most numeric data in USERS.BBS is stored
as 2-byte (16-bit) signed integers, which have a maximum positive value
of 32,767. If you have a user who's managed to logon 32,768 times or
post 32,768 messages, he'll overflow RAStat's capabilities (and RA's).
RAStat Documentation Page 11 of 14
════════════════════════════════════════════════════════════════════════
Nonetheless, RAStat does have a few limitations of its own. Most are
cosmetic, to insure that the program's output files don't exceed 80
characters in width. String fields, such as user names, are truncated
to fit if necessary. It's rather doubtful that you'll ever exceed
RAStat's numeric capabilities, but if you do, no real harm will be
done: the resulting output files just won't be very pretty.
For the record, here's the full rundown:
■ String fields
User names: 25 characters
User locations: 24 characters
User BPS rates: 5 characters (fixed: 300, 1200, 2400, 4800, 7200,
9600, 12000, 14400, 19200, 38400 or Local)
System names: 30 characters
Node number: 13 characters (sufficient for xxx:yyyy/zzzz, point
numbers are never displayed)
Dates: 8 characters (fixed: mm/dd/yy)
Times: 5 characters (fixed: hh:mm)
■ Numeric fields:
Total ul/dl: modified floating point, 6 digits (0 to 999,999)
Total upmb/dnmb: modified floating point, 6 digits (0 to 9999.99)
Total msgs: modified floating point, 6 digits (0 to 999,999)
Avg ul/dl: modified floating point, 6 digits (0 to 9999.99)
Avg upkb/dnkb: modified floating point, 6 digits (0 to 9999.99)
Avg msgs: modified floating point, 6 digits (0 to 9999.99)
Cost: modified integer, 4 digits (0 to 9999, with the
string character "¢" appended)
Bytes rx/tx: modified long integer, 8 digits (0 to 99,999,999)
Total rx/tx: long integer, 10 digits (0 to 2,147,483,648)
All other: integer, 5 digits (0 to 32,767)
■ Miscellaneous:
Max calls/day: 255 (ie: 255 entries each, user/inbound/outbound)
Max *.BBS files: limited only by available RAM
Max *.HIS files: limited only by available RAM
Min USERS.BBS: 11 records, not including excluded users
RAStat Documentation Page 12 of 14
════════════════════════════════════════════════════════════════════════
Program Errors:
───────────────
All "expected" external errors are trapped by the program. "Expected
errors" include just about every mistake you can make in configuring or
running RAStat (bad file names, invalid control file options, etc.), and
all of the routine external problems you might encounter (missing paths,
insufficient diskspace, etc). If RAStat aborts due to any of these
external errors, the program will display an error-specific help screen
that explains exactly what's wrong and how to fix it.
RAStat does not set DOS errorlevels on exit, and it has no logging
capabilities.
Revision History:
─────────────────
■ v0.1α Initial structures defined. Stats mode and ASCII write
routines implemented. Developmental testing.
■ v0.2α Existing code refined. Calls mode (user) routines
implemented. Developmental testing.
■ v0.3α Existing code refined. FDCalls, control file and error-
handling routines implemented. Developmental testing.
■ v0.4α Existing code refined. ANSI write routines implemented.
Alpha testing on 1:202/302.
■ v0.5ß Existing code optimized for improved speed and memory
management. Beta testing on 1:202/302 and 1:202/501.
■ v0.6ß Final beta version. Minor bugfixes and cosmetic changes.
Beta testing on 1:202/302 and 1:202/501.
■ v1.00 First public release. Distributed via SDS.
Planned future enhancements for RAStat include a small database function
that will allow generation of perpetual system statistics and other
long-term, historical information that the existing RA structures don't
provide for.
A companion program, FDStat, is also in the design stages. It will
include the capabilities of RAStat's FDCalls feature, together with
other FD-specific functions.
RAStat Documentation Page 13 of 14
════════════════════════════════════════════════════════════════════════
Contacting the Author:
──────────────────────
I welcome any comments regarding RAStat, and suggestions for future
versions. The program has been thoroughly tested and is believed to be
error-free, but if you discover an error, bug reports will certainly be
appreciated. Flames are never dignified with a response.
I prefer to communicate via electronic mail, and can be reached as
follows:
■ BBS: Gandalf's, 619-466-9505, 300-14400 bps HST, 8N1, 24 hrs
■ FidoNet: 1:202/302.0
■ Usenet: gryno@gandalfs.UUCP (ucsd!serene!jbbs!gandalfs!gryno)
or: gryno@f302.n202.z1.fidonet.org
■ CompuServe: 70671/1660
■ Bix: gryno
The latest version of RAStat is always available for download (first
call) on my BBS, at the above number. Nodelisted FidoNet SysOps (2400 bps
or faster) may also FReq the latest version from me using magic name
RASTAT, anytime except ZMH. Major revisions will be distributed via SDS.
Acknowledgements:
─────────────────
Special thanks to Frank Hicinbothem, 1:202/501... beta tester, friend,
trusted adviser, and general guru.
Thanks to the Software Distribution System (SDS) nodes for distributing
RAStat and countless other fine programs at their own expense.
RemoteAccess is a trademark of Andrew Milner and Continental Software.
The RemoteAccess Avatar Conversion Utility (AVTCONV) is a copyright-
protected program written by S/e/m/a/j Communications.
FrontDoor is a trademark of Joaquim Homrighausen and Advanced
Engineering sarl.
DESQview is a trademark of Quarterdeck Office Systems, Inc.
PKLite is a trademark of Phil Katz and PKWare.
LZExe is a freeware program written by Fabrice Bellard of Grabels, France.
Stacker is a trademark of Stac Electronics.
IBM PC, PC/XT and PC/AT are trademarks of IBM.
RAStat Documentation Page 14 of 14
════════════════════════════════════════════════════════════════════════
Dedication:
───────────
With great esteem and respect, RAStat is dedicated to the memory of:
Robert Michael Ivins (August 3, 1947 - March 9, 1991)
Photojournalist,
San Diego Union/Tribune Newspaper
United Press International
Associated Press
Winner, Pulitzer Prize